The last GitHub release reached v7.0.25, but the npm registry still reported @imdeadpool/guardex@7.0.24. This bumps the package to 7.0.26, records the matching README release note, and keeps the lane release-only so the next GitHub release can drive a clean publish retry from current main.

Constraint: npm cannot republish an existing version once GitHub release metadata is already ahead of the registry
Rejected: Reuse 7.0.25 | npm registry still shows 7.0.24, so a fresh semver is required for another publish attempt
Confidence: high
Scope-risk: narrow
Directive: Keep release-only lanes limited to semver plus README release notes unless the publish failure points back to package metadata or workflow code
Tested: node --check bin/multiagent-safety.js; openspec validate --specs; node --test test/metadata.test.js; node --test test/release.test.js; npm pack --dry-run
Not-tested: full npm test clean exit; this run hung after passing printed subtests because test/sandbox.test.js left a child codexAgent process alive